Method and system barcode-enabled payments

ABSTRACT

A method for facilitating a transaction with a one-time number includes: receiving a first transaction request, wherein the first transaction request includes a plurality of data elements including at least a first data element configured to store a zero transaction amount and a second data element configured to store a primary account number; parsing the primary account number stored in the second data element included in the received first transaction request; generating a one-time value, wherein the one-time value includes a predetermined number of digits and a subset of the predetermined number of digits is a reference to the processing server; storing a data entry comprised of at least the parsed primary account number and the generated one-time value; and transmitting the generated one-time value in response to the received first transaction request.

FIELD

The present disclosure relates to transactions utilizing a one-timenumber, specifically the use of mapping to enable one-time numbers to beused to conduct payment transactions through barcodes or other similarmeans that are funded by transaction accounts that are identified viathe mapping.

BACKGROUND

With the increasing prevalence of computing devices, many methods havebeen developed to enable a computing device to be used to fund anelectronic payment transaction. Originally, a user could manually inputpayment details into their computing device, which would be transmittedfor processing in the payment transaction, such as via a web page orother similar application program. As technology became more advanced,electronic wallets were developed, which were specialized applicationprograms that utilized more secure methods of storage to store paymentcredentials, which could be electronically transmitted to a merchantpoint of sale through a network (e.g., the Internet) or even directly,such as via near field communication for an in-purchase transaction.Traditionally, electronic wallets have operated by storing all of thesame data that would be stored in a payment card and conveying it to apoint of sale, where the point of sale receives the same data that itwould if reading the payment card directly, effectively trading apayment card for a mobile device that acts as a payment card.

In more recent times, some entities have developed their own kinds ofelectronic wallets, such as Alipay® that use alternative methods to payfor payment transactions. In such wallets, the wallet may generateunique data that is provided to the merchant, where the merchant routesthat data back to the provider of the wallet or an associated financialinstitution that can identify a related, pre-funded, cash balanceaccount to be used to fund the transaction. Such methods provide forgreater security than standard electronic wallets, as the unique datamay be usable for only a single transaction, and may only be processedthrough merchants that are configured to receive and use such data,where the provider of the wallet acts as a payment service provider forthe transaction. One common type of unique data is a one-time number.

However, current systems that utilize one-time numbers require the useof transaction accounts that are issued or otherwise managed by theprocessors of the one-time number. Such a processor would have to havethe account information stored in its system in order to pass thetransaction onto another payment processor, which would be a securityrisk and require additional input communications and interactions withthe consumer, the one-time number processor, and one or more paymentprocessors. As a result, this limits the abilities for consumers tofreely select how to fund such transaction, and may, in turn, limit theusage of one-time numbers, which may disadvantage the associatedentities as well as merchants that may lack the ability to processpayment transactions that utilize traditional payment credentials. Thus,there is a need for a technological solution to enable a one-time numberto be used for a transaction that is funded via an external transactionaccount without the problems associated with setting up an one-timepayment number processor to have multiple payment processor fundingsources as identified about and otherwise known.

SUMMARY

The present disclosure provides a description of systems and methods forfacilitating transactions with a one-time number using traditionalpayment rails to facilitate the request for generation of a one-timepayment number that would be funded by a consumer selected fundingsource that is a payment card account from an issuer that can transacton those rails. The issuer can then generate the one-time use number (ora reference number identifying same) that is sent to the wallet providerto be transmitted to the consumer. The wallet provider enables theconsumer to generate and display a bar code to the merchant at a pointof sale (POS), and the transaction authorization is sent to the walletprovider. The wallet provider system recognizes the one-time use numberand forwards it (or the reference number) for authorization and theresult of that authorization is then sent to the wallet provider system,which in turn forwards its decision to the merchant. This way, atraditional transaction account can be used to fund a transaction thatdoes not occur on payment rails, but is instead a transaction using aone-time number with an associated wallet provider, and withoutrequiring multiple transmissions form the consumer, the wallet provideror the merchant, all while keeping the actual payment card accountdetails out of the merchant and wallet systems for greater security.

A user may select a transaction account that they would like to use in afuture transaction where a one-time number would need to be used. Atransaction having a zero or nominal amount may be processed using theselected transaction account, which enables a back-end system togenerate a one-time number that is then mapped to that transactionaccount. The one-time number is provided back to the user, who may thenuse the one-time number (e.g., encoded in a machine-readable codedisplayed by their computing device) for a future payment transactioninvolving a merchant or wallet provider configured to processtransactions with one-time numbers. During the processing of thetransaction with the one-time number, the transaction may be routed tothe back-end system, which may identify the transaction account mappedto the one-time number and then process the transaction using thattransaction account. As a result, a payment transaction may be conductedusing a one-time number, but funded via a standard transaction account,utilizing the mapping and routing facilitated by the back-end system.Thus, merchants and wallet providers that are only configured to utilizeone-time numbers may still process payment transactions funded byexternal transaction accounts, providing for more opportunities withconsumers, while also enabling consumers to have free choice of thetransaction account used to fund transactions at such merchants.

A method for facilitating a transaction with a one-time number includes:receiving, by a receiver of a processing server, a first transactionrequest, wherein the first transaction request includes a plurality ofdata elements including at least a first data element configured tostore a zero transaction amount and a second data element configured tostore a primary account number; parsing, by the processing server, theprimary account number stored in the second data element included in thereceived first transaction request; generating, by the processingserver, a one-time value, wherein the one-time value includes apredetermined number of digits and a subset of the predetermined numberof digits is a reference to the processing server; storing, in a memoryof the processing server, a data entry comprised of at least the parsedprimary account number and the generated one-time value; andelectronically transmitting, by a transmitter of the processing server,the generated one-time value in response to the received firsttransaction request.

A system for facilitating a transaction with a one-time number includes:a receiver configured to receive a first transaction request, whereinthe first transaction request includes a plurality of data elementsincluding at least a first data element configured to store a zerotransaction amount and a second data element configured to store aprimary account number; a processing server configured to parse theprimary account number stored in the second data element included in thereceived first transaction request, and generate a one-time value,wherein the one-time value includes a predetermined number of digits anda subset of the predetermined number of digits is a reference to theprocessing server; a memory of the processing server configured to storea data entry comprised of at least the parsed primary account number andthe generated one-time value; and a transmitter of the processing serverconfigured to electronically transmit the generated one-time value inresponse to the received first transaction request.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

The scope of the present disclosure is best understood from thefollowing detailed description of exemplary embodiments when read inconjunction with the accompanying drawings. Included in the drawings arethe following figures:

FIG. 1 is a block diagram illustrating a high level system architecturefor facilitating payment transactions involving one-time numbers inaccordance with exemplary embodiments.

FIG. 2 is a block diagram illustrating the processing server of thesystem of FIG. 1 for facilitating payment transactions involvingone-time numbers in accordance with exemplary embodiments.

FIG. 3 is a flow diagram illustrating a process for the provisioning ofa one-time number mapped with a transaction account to a computingdevice using the system of FIG. 1 in accordance with exemplaryembodiments.

FIG. 4 is a flow diagram illustrating a process for the use of aone-time number mapped with a transaction account in a paymenttransaction using the system of FIG. 1 in accordance with exemplaryembodiments.

FIG. 5 is a flow chart illustrating an exemplary method for facilitatinga transaction with a one-time number in accordance with exemplaryembodiments.

FIG. 6 is a block diagram illustrating a computer system architecture inaccordance with exemplary embodiments.

Further areas of applicability of the present disclosure will becomeapparent from the detailed description provided hereinafter. It shouldbe understood that the detailed description of exemplary embodiments areintended for illustration purposes only and are, therefore, not intendedto necessarily limit the scope of the disclosure.

DETAILED DESCRIPTION Glossary of Terms

Payment Network—A system or network used for the transfer of money viathe use of cash-substitutes for thousands, millions, and even billionsof transactions during a given period. Payment networks may use avariety of different protocols and procedures in order to process thetransfer of money for various types of transactions. Transactions thatmay be performed via a payment network may include product or servicepurchases, credit purchases, debit transactions, fund transfers, accountwithdrawals, etc. Payment networks may be configured to performtransactions via cash-substitutes, which may include payment cards,letters of credit, checks, transaction accounts, etc. Examples ofnetworks or systems configured to perform as payment networks includethose operated by MasterCard®, VISA®, Discover®, American Express®,PayPal®, etc. Use of the term “payment network” herein may refer to boththe payment network as an entity, and the physical payment network, suchas the equipment, hardware, and software comprising the payment network.

Transaction Account—A financial account that may be used to fund atransaction, such as a checking account, savings account, creditaccount, virtual payment account, etc. A transaction account may beassociated with a consumer, which may be any suitable type of entityassociated with a payment account, which may include a person, family,company, corporation, governmental entity, etc. In some instances, atransaction account may be virtual, such as those accounts operated byPayPal®, etc.

Payment Rails—Infrastructure associated with a payment network used inthe processing of payment transactions and the communication oftransaction messages and other similar data between the payment networkand other entities interconnected with the payment network that handlesthousands, millions, and even billions of transactions during a givenperiod. The payment rails may be comprised of the hardware used toestablish the payment network and the interconnections between thepayment network and other associated entities, such as financialinstitutions, gateway processors, etc. In some instances, payment railsmay also be affected by software, such as via special programming of thecommunication hardware and devices that comprise the payment rails. Forexample, the payment rails may include specifically configured computingdevices that are specially configured for the routing of transactionmessages, which may be specially formatted data messages that areelectronically transmitted via the payment rails, as discussed in moredetail below.

Merchant—An entity that provides products (e.g., goods and/or services)for purchase by another entity, such as a consumer or another merchant.A merchant may be a consumer, a retailer, a wholesaler, a manufacturer,or any other type of entity that may provide products for purchase aswill be apparent to persons having skill in the relevant art. In someinstances, a merchant may have special knowledge in the goods and/orservices provided for purchase. In other instances, a merchant may nothave or require any special knowledge in offered products. In someembodiments, an entity involved in a single transaction may beconsidered a merchant. In some instances, as used herein, the term“merchant” may refer to an apparatus or device of a merchant entity.

Issuer—An entity that establishes (e.g., opens) a letter or line ofcredit in favor of a beneficiary, and honors drafts drawn by thebeneficiary against the amount specified in the letter or line ofcredit. In many instances, the issuer may be a bank or other financialinstitution authorized to open lines of credit. In some instances, anyentity that may extend a line of credit to a beneficiary may beconsidered an issuer. The line of credit opened by the issuer may berepresented in the form of a payment account, and may be drawn on by thebeneficiary via the use of a payment card. An issuer may also offeradditional types of payment accounts to consumers as will be apparent topersons having skill in the relevant art, such as debit accounts,prepaid accounts, electronic wallet accounts, savings accounts, checkingaccounts, etc., and may provide consumers with physical or non-physicalmeans for accessing and/or utilizing such an account, such as debitcards, prepaid cards, automated teller machine cards, electronicwallets, checks, etc.

Acquirer—An entity that may process payment card transactions on behalfof a merchant. The acquirer may be a bank or other financial institutionauthorized to process payment card transactions on a merchant's behalf.In many instances, the acquirer may open a line of credit with themerchant acting as a beneficiary. The acquirer may exchange funds withan issuer in instances where a consumer, which may be a beneficiary to aline of credit offered by the issuer, transacts via a payment card witha merchant that is represented by the acquirer.

Payment Transaction—A transaction between two entities in which money orother financial benefit is exchanged from one entity to the other. Thepayment transaction may be a transfer of funds, for the purchase ofgoods or services, for the repayment of debt, or for any other exchangeof financial benefit as will be apparent to persons having skill in therelevant art. In some instances, payment transaction may refer totransactions funded via a payment card and/or payment account, such ascredit card transactions. Such payment transactions may be processed viaan issuer, payment network, and acquirer. The process for processingsuch a payment transaction may include at least one of authorization,batching, clearing, settlement, and funding. Authorization may includethe furnishing of payment details by the consumer to a merchant, thesubmitting of transaction details (e.g., including the payment details)from the merchant to their acquirer, and the verification of paymentdetails with the issuer of the consumer's payment account used to fundthe transaction. Batching may refer to the storing of an authorizedtransaction in a batch with other authorized transactions fordistribution to an acquirer. Clearing may include the sending of batchedtransactions from the acquirer to a payment network for processing.Settlement may include the debiting of the issuer by the payment networkfor transactions involving beneficiaries of the issuer. In someinstances, the issuer may pay the acquirer via the payment network. Inother instances, the issuer may pay the acquirer directly. Funding mayinclude payment to the merchant from the acquirer for the paymenttransactions that have been cleared and settled. It will be apparent topersons having skill in the relevant art that the order and/orcategorization of the steps discussed above performed as part of paymenttransaction processing.

Point of Sale—A computing device or computing system configured toreceive interaction with a user (e.g., a consumer, employee, etc.) forentering in transaction data, payment data, and/or other suitable typesof data for the purchase of and/or payment for goods and/or services.The point of sale may be a physical device (e.g., a cash register,kiosk, desktop computer, smart phone, tablet computer, etc.) in aphysical location that a customer visits as part of the transaction,such as in a “brick and mortar” store, or may be virtual in e-commerceenvironments, such as online retailers receiving communications fromcustomers over a network such as the Internet. In instances where thepoint of sale may be virtual, the computing device operated by the userto initiate the transaction or the computing system that receives dataas a result of the transaction may be considered the point of sale, asapplicable.

Processing of One-Time Number Transactions with Mapped TransactionAccounts

FIG. 1 illustrates a system 100 for the processing of paymenttransactions that utilize one-time numbers that are funded by standardtransaction accounts mapped thereto via the use of a back-end processingsystem.

The system 100 may include a processing server 102. The processingserver 102, discussed in more detail below, may be configured to performmapping of transaction account credentials to one-time numbers for usethereof in funding transactions conducted with one-time numbers with themapped transaction accounts. As used herein, “one-time number” may referto a number or any other type of data that may be used for a singletransaction that includes data suitable for use in performing thefunctions discussed herein. For instance, an alphanumeric value or othertype of data may be used as an alternative to the one-time number. Asdiscussed herein, a one-time number may be encoded in a machine-readablecode that is displayed for use in conveyance thereof. Themachine-readable code may be any type of code suitable for encoding theone-time number, such as a bar code or a quick response (QR) code. Theone-time number may include at least an identification value, where anyother data included in the one-time number may be referred to herein as“remaining value.” In one embodiment, the one-time number may be an 18digit number, where the first two digits may be the identificationvalue, and where the other 16 digits may be the remaining value.

In the system 100, a consumer may be interested in conducting a paymenttransaction with a one-time number that is funded via a transactionaccount not issued or managed by a wallet provider 106 that isconfigured to process one-time number transactions as a payment serviceprovider. The consumer may possess a computing device 104, which may beused to obtain a one-time number that is mapped to the desiredtransaction account, to enable the transaction account to be used tofund a payment transaction that is processed via the one-time number.The computing device 104 may be any type of device suitable forperforming the functions discussed herein, such as a laptop computer,notebook computer, tablet computer, cellular phone, smart phone, smartwatch, wearable computing device, implantable computing device, etc.

The system 100 may include an issuing institution 108. The issuinginstitution 108 may be a financial institution, such as an issuing bank,or other entity configured to issue transaction accounts for use infunding electronic payment transactions. The issuing institution 108 mayissue a transaction account to the consumer that may be used inelectronic payment transactions. As part of the issuing of thetransaction account, the issuing institution 108 may provision paymentcredentials associated with the transaction account to the computingdevice 104 using a suitable method. The payment credentials may includea transaction account number or a tokenized version of a transactionaccount number and any other data necessary for the funding of anelectronic payment transaction by the corresponding transaction account,such as may include a name, expiration date, security code, transactioncounter, payment cryptogram, etc. The payment credentials may be storedin the computing device 104 using any suitable method, such as in asecure element or other secured data storage. In some cases, thecomputing device 104 may include an electronic wallet applicationprogram associated with the issuing institution 108 for the receipt andstorage of the payment credentials.

Prior to the conducting of the one-time number transaction, the consumermay use the computing device 104 to request a one-time number from theprocessing server 102. The computing device 104 may electronicallytransmit a transaction request to the processing server 102 using asuitable communication network and method. In some cases, thetransaction request may be submitted through an electronic walletapplication program or an application programming interface (API)associated with the processing server 102. In an exemplary embodiment,the transaction request may be an authorization request or othertransaction message for an electronic payment transaction. In such anembodiment, the computing device 104 may initiate a payment transactionwith the processing server 102, where the payment transaction may befunded by the transaction account issued by the issuing institution 108and include the payment credentials associated therewith, but where thetransaction amount may be zero or a nominal value. In some suchembodiments, the transaction request may be a transaction messageformatted according to one or more standards governing the interchangeof financial transaction messages, such as the InternationalOrganization of Standardization's ISO 8583 or ISO 20022 standards. Insuch cases, the transaction message may include a message type indicatorindicative of an authorization request and may include a plurality ofdata elements including data elements configured to store the zero ornominal value transaction amount, the primary account number for thetransaction account, and any other payment credentials that may benecessary.

The processing server 102 may receive the transaction request. Theprocessing server 102 may identify that the transaction requestcorresponds to a request for one or more one-time numbers based on atleast the zero or nominal value transaction amount. In some cases, thetransaction message may include additional data values in one or moredata elements that may indicate that the transaction corresponds to arequest for a one-time number. The processing server 102 may parse theprimary account number and any other payment credentials from thetransaction message. The processing server 102 may then generate orotherwise identify one or more one-time numbers. The one-time number(s)may include at least an identification value that corresponds to or mayotherwise identify or reference the processing server 102. In somecases, the identification value, or a separate portion of the one-timenumber, may reference the wallet provider 106. In some embodiments, theprocessing server 102 may generate the one-time number using internalprocessing systems. In other embodiments, the processing server 102 maybe configured to obtain the one-time number from the wallet provider106. In some cases, the processing server 102 may request the one-timenumber after receipt of the transaction request from the computingdevice 104. In other cases, the wallet provider 104 may provide theprocessing server 102 with one-time numbers periodically, which theprocessing server 102 may use as transaction requests are received.

Following identification of the one-time number, the processing server102 may map the one-time number to the primary account number and anyother payment credentials received in the transaction request. Themapping may include the storage of a data pair in internal or externalmemory of the processing server 102, wherein the data pair consists ofthe one-time number and the payment credentials for the transactionaccount. The processing server 102 may then provide the one-time numberto the computing device 104. In some embodiments, the processing server102 may perform standard processing of the attempted electronic paymenttransaction for the zero or nominal amount, where the transaction may beapproved or denied (e.g., by the issuing institution 108 or processingserver 102 on behalf thereof) and an authorization response returned tothe computing device 104. For example, the transaction may be approvedif for a zero transaction amount or may be declined if for a nominaltransaction amount to prevent any payments made by the consumer inobtaining the one-time value. In some such embodiments, theauthorization response may include the one-time number in a data elementthereof. In other embodiments, the one-time number may be electronicallytransmitted to the computing device 104 separately from an authorizationresponse. In such embodiments, the processing server 102 may receivecommunication data for use in identifying and communicating with thecomputing device 104 via the transaction request or other suitablemethod. For instance, the computing device 104 may be registered withthe processing server 102 as associated with the transaction account,such as through the application program or API. In some embodiments, theone-time number may be encrypted or otherwise protected in transmissionfrom the processing server 102 to the computing device 104.

The computing device 104 may thus receive the one-time number from theprocessing server 102. The computing device 104 may then use theone-time number in an electronic payment transaction to be conductedthrough, with, or otherwise involving the wallet provider 106 as apayment service provider for the transaction. For example, the computingdevice 104 may be configured to generate a machine-readable code that isencoded with the one-time number, which may be displayed on a displaydevice interfaced therewith that is read by a merchant point of saledevice 112. The point of sale device 112 may decode the one-time numbertherefrom and submit it to the wallet provider 106. In some cases, theone-time number may include a second identification value that isassociated with the wallet provider 106 for use by the point of saledevice 112 in routing the one-time number thereto. The merchant point ofsale device 112 may also submit transaction data for the attemptedelectronic payment transaction to the wallet provider 106, which mayinclude, for instance, a transaction amount or any other data that maybe necessary or desired for the payment transaction, such as atransaction time, transaction date, merchant identification number,merchant category code, product data, offer data, reward data, loyaltydata, point of sale data, currency type, etc. In some embodiments, thewallet provider 106 may be the point of sale device 112 and may receivethe one-time number directly from the computing device 104 as part ofthe attempted electronic payment transaction.

The wallet provider 106 may thus obtain the one-time number as well asany transaction data for the payment transaction. The wallet provider106 may identify the identification value included in the one-timenumber as being a reference to or otherwise associated with theprocessing server 102. The wallet provider 106 may then submit atransaction request to the processing server 102 for the one-time numbertransaction, where the transaction request includes at least theone-time number, transaction amount, and any other transaction data. Insome embodiments, the wallet provider 106 may forward a transactionrequest received from a point of sale device 112 directly to theprocessing server 102 upon identification of the identification valueincluded in the one-time number. In some cases, the transaction requestsubmitted to the processing server 102 may be an authorization requestfor an electronic payment transaction, where the one-time number isstored in a data element configured for the storage of a primary accountnumber according to the applicable standard(s).

The processing server 102 may thus receive the one-time number,transaction amount, and any other transaction data related to theelectronic payment transaction initiated with the one-time number. Theprocessing server 102 may then identify the payment credentials (e.g.,at least the primary account number and any other data, as applicable)that are mapped to the one-time number. The processing server 102 mayreplace the one-time number in the authorization request with theprimary account number and may otherwise update the data elements in theauthorization request with the mapped payment credentials. In someembodiments, the processing server 102 may generate a new authorizationrequest that includes the payment credentials. For instance, the walletprovider 106 may submit a transaction request to the processing server102 that may utilize different standards than in electronic paymenttransactions funded via traditional transaction accounts. In such aninstance, the processing server 102 may generate an authorizationrequest that is formatted according to standards associated withtraditional transaction accounts. The authorization request may includethe payment credentials and any additional transaction data included inthe received transaction request that may be used in traditionalelectronic payment transaction processing. In some embodiments, theprocessing server 102 may be configured to perform risk assessmentsprior to the generation or submission of the authorization request. Forinstance, the processing server 102 may check any restrictions orlimitations placed on the one-time number, as discussed below, mayperform fraud scoring or other analysis of the proposed transaction, mayperform a timestamp check, or other assessment to determine if thetransaction should proceed.

Once the processing server 102 has generated or otherwise obtained theauthorization request including the payment credentials, theauthorization request may be submitted to a payment network 110 forprocessing via payment rails associated therewith. The payment network110 may then process the payment transaction using traditional methodsand systems, which may include submitting the authorization request tothe issuing institution 108 for approval or denial of the paymenttransaction and receipt of an authorization response therefrom. As partof the processing, the payment network 110 may return an authorizationresponse to the processing server 102, where the authorization responsemay be formatted according to the applicable standard(s) and may includea data element configured to store a response code indicating approvalor denial of the payment transaction. In some embodiments, theprocessing server 102 may be configured to receive the one-time numberfrom the payment network 110 via payment rails associated therewith,such as through submission of the one-time number to the point of saledevice 112. Additional detail regarding the use of payment rails for theconveyance of one-time numbers can be found in U.S. patent applicationSer. No. 15/793,237, entitled “Method and System for Conveyance ofMachine Readable Code Data via Payment Network,” filed on Oct. 25, 2017,which is herein incorporated by reference in its entirety.

Once an authorization response is received from the payment network 110,the processing server 102 may return a response to the transactionrequest to the wallet provider 106. In some cases, the processing server102 may forward the authorization response to the wallet provider 106,but may first replace the primary account number and any other paymentcredentials with the mapped one-time number. In other cases, theprocessing server 102 may provide a response to the transaction requestthat is formatted according to standards applicable to the transactionrequest, which may be separate from standards applicable to theauthorization response. The wallet provider 106 may receive thetransaction response from the processing server 102 and then finalizethe one-time number transaction accordingly (e.g., based on the approvalor denial of the payment transaction by the issuing institution 108). Asa result, the one-time number transaction may be funded (e.g., ifapproved) by the standard transaction account via the use of theprocessing server 102 and mapping of the payment credentials for thetransaction account to a one-time number.

In some embodiments, restrictions may be placed on the one-time numberissued to the computing device 104 by the processing server 102. Forinstance, in some cases, the one-time number may be limited in the timeduring which it may be used. In one example, the one-time number mayhave a predetermined period of time during which it must be used in atransaction through the wallet provider 106 or else any transactionattempted using the one-time number may be declined. Such a time outmechanism may prevent unauthorized using of the payment credentials,such as in cases where the computing device 104 may be stolen. In someinstances, the one-time number itself may include data indicating suchrestrictions, such as an expiration time and/or date being included inthe one-time number. In other instances, the processing server 102 maystore such information (e.g., in the data pair used for mapping) and mayutilize such information when performing the mapping upon receipt of thetransaction request. In some embodiments, the processing server 102 mayissue multiple one-time numbers to the computing device 104 for use in aseries of transactions. In some such embodiments, one or more of theone-time numbers may be available for use by the computing device 104offline (e.g., without an active Internet or other communication channelcapable of communicating with the processing server 102). In such anembodiment, the one-time numbers available for offline use may haverestrictions placed thereon, such as an expiration time and/or date,which may be updated if the computing device 104 goes back online (e.g.,the expiration date may be extended by the processing server 102 once incommunication with the computing device 104).

In some cases, the processing server 102 may perform authentication ofthe consumer prior to issuing of the one-time number. For instance, theprocessing server 102 may require the consumer to provide authenticationinformation (e.g., username, password, personal identification number,etc.), which must be authenticated prior to the issuance of the one-timenumber. In some embodiments, the processing server 102 may alternativelyor additionally authenticate the computing device 104 itself, such as toensure that the computing device 104 has not been compromised. Forexample, the processing server 102 and computing device 104 may performa mutual authentication prior to issuance of the one-time number. Insome instances, one or more functions of the processing server 102 maybe performed by the computing device 104, such as in cases where acommunication channel between the processing server 102 and computingdevice 104 may be unavailable. For instance, the processing server 102may provide the computing device 104 with one-time numbers for use thatare mapped to the transaction account ahead of time, which may besecurely stored in the computing device 104 and unavailable for useuntil such a time as requested by the consumer, which may requireadditional authentication to be performed.

In some cases, the one-time number may be associated with additionaldata in addition to a transaction account. For instance, in oneembodiment, a one-time number may be associated with a coupon or otherdeal, discount, or redeemable object. In such embodiments, theprocessing server 102 may receive the one-time number and identify thecorresponding redeemable object. The processing server 102 may thenperform any actions associated with the redemption of the redeemableobject (e.g., discounting of the transaction if the redeemable object isa coupon) and then process the transaction as discussed above. In someinstances, the one-time number associated with the redeemable object maybe mapped to a second one-time number (e.g., associated with thetransaction account, as discussed above), which may then be mapped tothe transaction account, as discussed above. In some cases, one-timenumbers associated with redeemable objects may be formatted differentlyor otherwise indicate their association with a redeemable object asopposed to a transaction account. For example, one-time numbers forredeemable objects may have a different number of digits or have aunique identifier in a different range from unique identifiers fortransaction account one-time numbers.

In some embodiments, the computing device 104 may be provided with anelectronic receipt for the payment transaction. The electronic receiptmay be provided by the wallet provider 106 (e.g., through the point ofsale device 112), the processing server 102, or a third party entityconfigured to provide receipts for processed transactions. Theelectronic receipt may include transaction data for the paymenttransaction including a unique identifier associated with thetransaction, such as an identification number or other suitable value.In some cases, the unique identifier may be the one-time number. In someinstances, the computing device 104 may be configured to present theelectronic receipt for refunding of the processed transaction. Forinstance, the computing device 104 may electronically transmit theunique identifier to the wallet provider 106 (e.g., via the point ofsale device 112), which may use the unique identifier to identify thepreviously processed transaction. The wallet provider 106 may thenforward the one-time number or other data for the transaction to theprocessing server 102 in a request for a refund. The processing server102 may then identify the transaction account used to fund thetransaction and refund the processed transaction using traditionalmethods and systems. In some cases, the computing device 104 may submitthe request for a refund directly to the processing server 102.

The methods and systems discussed herein thus enable wallet providers106 and merchants that are configured to utilize one-time numbers tocontinue to do so while enabling consumers to fund such transactionswith traditional transaction accounts. The result is that merchants andwallet providers 106 can expand their customer base and increase theirtransaction capabilities, while at the same time providing consumerswith greater convenience in providing them to freely select transactionaccounts for use in funding payment transactions for both standard andone-time number transactions. The processing server 102 thereforeprovides a technological improvement to transaction processing systemsby enabling traditional transaction accounts to be used to fund paymenttransactions initiated via one-time numbers through the use of aninitial zero or nominal payment transaction that facilitates mapping ofpayment credentials with a one-time number that can be utilized when atransaction is attempted using that one-time number. This also, as aresult, facilitates the use of a traditional transaction account to fundpayment transactions conducted using a one-time number, which may beperformed without transmissions utilizing payment rails or other paymentnetwork infrastructure.

Processing Server

FIG. 2 illustrates an embodiment of a processing server 102 in thesystem 100. It will be apparent to persons having skill in the relevantart that the embodiment of the processing server 102 illustrated in FIG.2 is provided as illustration only and may not be exhaustive to allpossible configurations of the processing server 102 suitable forperforming the functions as discussed herein. For example, the computersystem 600 illustrated in FIG. 6 and discussed in more detail below maybe a suitable configuration of the processing server 102.

The processing server 102 may include a receiving device 202. Thereceiving device 202 may be configured to receive data over one or morenetworks via one or more network protocols. In some instances, thereceiving device 202 may be configured to receive data from computingdevices 104, wallet providers 106, issuing institutions 108, paymentnetworks 110, and other systems and entities via one or morecommunication methods, such as radio frequency, local area networks,wireless area networks, cellular communication networks, Bluetooth, theInternet, etc. In some embodiments, the receiving device 202 may becomprised of multiple devices, such as different receiving devices forreceiving data over different networks, such as a first receiving devicefor receiving data over a local area network and a second receivingdevice for receiving data via the Internet. The receiving device 202 mayreceive electronically transmitted data signals, where data may besuperimposed or otherwise encoded on the data signal and decoded,parsed, read, or otherwise obtained via receipt of the data signal bythe receiving device 202. In some instances, the receiving device 202may include a parsing module for parsing the received data signal toobtain the data superimposed thereon. For example, the receiving device202 may include a parser program configured to receive and transform thereceived data signal into usable input for the functions performed bythe processing device to carry out the methods and systems describedherein.

The receiving device 202 may be configured to receive data signalselectronically transmitted by computing devices 104, which may besuperimposed or otherwise encoded with transaction requests, which maybe formatted according to standards governing the interchange offinancial transaction messages. The transaction requests may includepayment credentials and a zero or nominal transaction amount. Thereceiving device 202 may also be configured to receive data signalselectronically transmitted by wallet providers 106, which may besuperimposed or otherwise encoded with one-time numbers oridentification or remaining values to be included therein, or may besuperimposed or otherwise encoded with transaction requests for one-timenumber transactions, which may include one-time numbers, transactionamounts, and any other suitable transaction data. The receiving device202 may be configured to receive data signals electronically transmittedby issuing institutions 108, which may be superimposed or otherwiseencoded with payment credentials for mapping, authorization responsesfor attempted electronic payment transactions, or other data asdiscussed herein. The receiving device 202 may be further configured toreceive data signals electronically transmitted by payment networks 110,which may be superimposed or otherwise encoded with authorizationresponses for electronic payment transactions, which may be transmittedvia payment rails associated with the payment network 110.

The processing server 102 may also include a communication module 204.The communication module 204 may be configured to transmit data betweenmodules, engines, databases, memories, and other components of theprocessing server 102 for use in performing the functions discussedherein. The communication module 204 may be comprised of one or morecommunication types and utilize various communication methods forcommunications within a computing device. For example, the communicationmodule 204 may be comprised of a bus, contact pin connectors, wires,etc. In some embodiments, the communication module 204 may also beconfigured to communicate between internal components of the processingserver 102 and external components of the processing server 102, such asexternally connected databases, display devices, input devices, etc. Theprocessing server 102 may also include a processing device. Theprocessing device may be configured to perform the functions of theprocessing server 102 discussed herein as will be apparent to personshaving skill in the relevant art. In some embodiments, the processingdevice may include and/or be comprised of a plurality of engines and/ormodules specially configured to perform one or more functions of theprocessing device, such as a querying module 218, generation module 220,transaction processing module 222, etc. As used herein, the term“module” may be software or hardware particularly programmed to receivean input, perform one or more processes using the input, and provides anoutput. The input, output, and processes performed by various moduleswill be apparent to one skilled in the art based upon the presentdisclosure.

The processing server 102 may also include a memory 210. The memory 210may be configured to store data for use by the processing server 102 inperforming the functions discussed herein, such as public and privatekeys, symmetric keys, etc. The memory 210 may be configured to storedata using suitable data formatting methods and schema and may be anysuitable type of memory, such as read-only memory, random access memory,etc. The memory 210 may include, for example, encryption keys andalgorithms, communication protocols and standards, data formattingstandards and protocols, program code for modules and applicationprograms of the processing device, and other data that may be suitablefor use by the processing server 102 in the performance of the functionsdisclosed herein as will be apparent to persons having skill in therelevant art. In some embodiments, the memory 210 may be comprised of ormay otherwise include a relational database that utilizes structuredquery language for the storage, identification, modifying, updating,accessing, etc. of structured data sets stored therein.

The memory 210 may be configured to store, for example, data pairs usedfor mapping, which may include at least a primary account number (e.g.,and additional payment credentials, as applicable) and a one-time numbermapped thereto. In some cases, a data pair may further include anexpiration time and/or date or any other restrictions that may be placedthereon. In some cases, the memory 210 may store profiles associatedwith transaction accounts, where a profile may include multiple datapairs (e.g., for multiple one-time numbers issued on the sametransaction account) and any other data for use in performing thefunctions discussed herein, such as authentication data, usagerestrictions, communication data associated with a correspondingcomputing device 104, etc.

The processing server 102 may include a querying module 218. Thequerying module 218 may be configured to execute queries on databases toidentify information. The querying module 218 may receive one or moredata values or query strings, and may execute a query string basedthereon on an indicated database, such as the memory 210, to identifyinformation stored therein. The querying module 218 may then output theidentified information to an appropriate engine or module of theprocessing server 102 as necessary. The querying module 218 may, forexample, execute a query on the memory 210 to insert a new data pairtherein upon receipt of a transaction request from a computing device104 for a new mapping between a primary account number and one-timenumber. The querying module 218 may also be configured to executequeries on the memory 210 to identify previously stored data pairs foruse in mapping a one-time number included in a received transactionrequest to the corresponding payment credentials.

The processing server 102 may also include a generation module 220. Thegeneration module 220 may be configured to generate data for use by theprocessing server 102 in performing the functions discussed herein. Thegeneration module 220 may receive instructions as input, may generatedata based on the instructions, and may output the generated data to oneor more modules of the processing server 102. For example, thegeneration module 220 may be configured to generate one-time numbers,where each one-time number may include an identification valueassociated with or otherwise referencing the processing server 102 foruse in routing by the wallet provider 106 or other entity. Thegeneration module 220 may also be configured to generate transactionmessages for use in the processing of electronic payment transactions asdiscussed herein.

The processing server 102 may also include a transaction processingmodule 222. The transaction processing module 222 may be configured toperform functions associated with the processing of transactions as partof the processing server 102 as discussed herein. For example, thetransaction processing module 222 may be configured to initiate paymenttransactions for the funding of one-time number transactions usingtraditional transaction accounts, perform routing of authorizationrequests and responses, etc.

The processing server 102 may also include a transmitting device 224.The transmitting device 224 may be configured to transmit data over oneor more networks via one or more network protocols. In some instances,the transmitting device 224 may be configured to transmit data tocomputing devices 104, wallet providers 106, issuing institutions 108,payment networks 110, and other entities via one or more communicationmethods, local area networks, wireless area networks, cellularcommunication, Bluetooth, radio frequency, the Internet, etc. In someembodiments, the transmitting device 224 may be comprised of multipledevices, such as different transmitting devices for transmitting dataover different networks, such as a first transmitting device fortransmitting data over a local area network and a second transmittingdevice for transmitting data via the Internet. The transmitting device224 may electronically transmit data signals that have data superimposedthat may be parsed by a receiving computing device. In some instances,the transmitting device 224 may include one or more modules forsuperimposing, encoding, or otherwise formatting data into data signalssuitable for transmission.

The transmitting device 224 may be configured to electronically transmitdata signals to computing devices 104 that may be superimposed orotherwise encoded with responses to transaction requests, which mayinclude or be accompanied by one-time numbers, which may be encrypted orotherwise protected in transmission thereto. The transmitting device 224may also be configured to electronically transmit data signals to walletproviders 106, which may be superimposed or otherwise encoded withtransaction responses, which may be authorization responses formattedaccording to standards governing the interchange of financialtransaction messages, or may be superimposed or otherwise encoded withrequests for one-time numbers. The transmitting device 224 may befurther configured to electronically transmit data signals to issuinginstitutions 108, which may be superimposed or otherwise encoded withtransaction messages, requests for payment credentials, authenticationrequests, or other data as discussed herein. The transmitting device 224may also be configured to electronically transmit data signals topayment networks 110, which may be superimposed or otherwise encodedwith authorization requests, which may be submitted via payment railsassociated with the payment network 110.

Process for Provisioning of a One-Time Number to a Computing Device

FIG. 3 illustrates an example process executed in the system 100 of FIG.1 for the provisioning of a one-time number from the processing server102 to the computing device 104 that is mapped with payment credentialsassociated with a transaction account.

In step 302, the computing device 102 may receive account informationfrom the issuing institution 108, which may include payment credentialsassociated with a transaction account that are suitable for use infunding an electronic payment transaction with the associatedtransaction account. In step 304, the computing device 104 may submit arequest for a one-time number to the processing server 102 using asuitable communication network and method. For instance, the request maybe submitted via a web page, application program executed by thecomputing device 104, short messaging service message, e-mail, API ofthe processing server 102, etc. In an exemplary embodiment, the one-timenumber request may be submitted as a payment transaction having a zeroor nominal transaction amount, where the payment credentials aresupplied as the funding source for the payment transaction. In step 306,the receiving device 202 of the processing server 102 may receive therequest. The one-time number request may include at least the paymentcredentials associated with the transaction account for which theone-time number is requested. In some cases, the request may alsoinclude a period of time during which the one-time number is to be used,which may be used to set the expiration period for the one-time number.

In some embodiments, the process may include step 308, where the walletprovider 106 may supply one or more one-time numbers to the processingserver 102 using a suitable communication network and method for receiptby the receiving device 202 thereof. Step 308 may be an optional stepand may not be performed in cases where the processing server 102 isconfigured to generate one-time numbers without being supplied directlyby the wallet provider 106. In step 310, the generation module 220 ofthe processing server 102 may generate or otherwise identify (e.g., ifsupplied by the wallet provider 106) a one-time number. The one-timenumber may include at least an identification value that references theprocessing server 102. In some cases, the one-time number may furtherinclude a second identification value or the identification value mayadditional include data referencing the wallet provider 106.

In step 312, the querying module 218 of the processing server 102 mayexecute a query on the memory 210 of the processing server 102 to storea data pair therein mapping the generated one-time number with thepayment credentials received in the one-time number request. In caseswhere one or more restrictions may be placed on use of the one-timenumber, the data pair may further include the restrictions. In step 314,the transmitting device 224 of the processing server 102 mayelectronically transmit the one-time number to the computing device 104using a suitable communication network and method. In cases where theone-time number may be subject to restrictions, such data may beprovided with the one-time number. In an exemplary embodiment, theone-time number may be included in or may accompany an authorizationresponse or other response to an attempted payment transaction initiatedby the computing device 104 (e.g., as part of step 304). In step 316,the computing device 104 may receive the one-time number. In someembodiments, the process may include step 318, where the wallet provider106 may also be provided a copy of the one-time number. In step 320, thecomputing device 104 may store the one-time number therein for later usein an electronic payment transaction.

Process for Funding a One-Time Number Transaction with a TransactionAccount

FIG. 4 illustrates an example process executed in the system 100 of FIG.1 for the processing of a one-time number payment transaction that isfunded using a standard transaction account with traditional processingthereof.

In step 402, the computing device 104 may submit a one-time number(e.g., provisioned thereto using the process illustrated in FIG. 3 anddiscussed above) to a wallet provider 106 for use in an electronicpayment transaction utilizing the one-time number. The one-time numbermay be submitted to the wallet provider 106 (e.g., directly or via anintermediate system or entity, such as the point of sale device 112)using any suitable method, such as near field communication, radiofrequency, Bluetooth, short messaging service, e-mail, display in amachine-readable code read by the wallet provider 106, etc. In somecases, the one-time number may be included in a transaction message orother data message submitted to the wallet provider 106 as part of apayment transaction, such as may include a transaction amount and othersuitable data. In step 404, the wallet provider 106 may receive theone-time number. The one-time number may include at least anidentification value that references the processing server 102. In step406, the wallet provider 106 may parse the identification value form theone-time number that references the processing server 102.

In step 408, the wallet provider 106 may forward a transaction requestfor the electronic payment transaction to the processing server 102. Insome cases, the transaction request may be submitted by the computingdevice 104 (e.g., in step 402) and forwarded directly to the processingserver 102. In other cases, the wallet provider 106 may generate thetransaction request to include transaction data for the electronicpayment transaction and the one-time number received from the computingdevice 104. In step 410, the receiving device 202 of the processingserver 102 may receive the transaction request. The transaction requestmay include at least the one-time number, transaction amount, and anyother data suitable for use in the processing of an electronic paymenttransaction.

In step 412, the querying module 218 of the processing server 102 mayexecute a query on the memory 210 of the processing server 102 toidentify payment credentials that are mapped to the one-time number. Instep 414, the generation module 220 of the processing server 102 maygenerate an authorization request for a payment transaction thatincludes the identified payment credentials and the transaction amountand any other data from the request received from the wallet provider106, which may be transmitted, by the transmitting device 224 of theprocessing server 102, to the payment network 110 via payment railsassociated therewith for processing. In step 416, the receiving device202 of the processing server 102 may receive an authorization responsefrom the payment network 110 via payment rails associated therewith forthe payment transaction, which may include a data element configured tostore a response code indicating approval or denial of the paymenttransaction.

In step 418, the transmitting device 224 of the processing server 102may forward an authorization response to the wallet provider 106. Insome cases, the authorization response may be the same authorizationresponse received from the payment network 110. In some such cases, thepayment credentials may be replaced with the one-time number prior toforwarding. In other cases, the generation module 220 of the processingserver 102 may generate a separate response to the transaction requestsubmitted by the wallet provider 104, which may be utilized as theauthorization response forwarded to the wallet provider 104. In step420, the wallet provider 106 may receive the authorization response fromthe processing server 102. In step 422, the wallet provider 106 mayperform any additional processing for the transaction based on thereceived authorization response, such as by furnishing the consumerassociated with the computing device 104 with transacted-for goods orservices. In step 424, the computing device 104 may receive anotification indicating if the transaction was approved or denied or anyother data associated with the processing of the one-time numbertransaction.

Exemplary Method for Facilitating a Transaction with a One-Time Number

FIG. 5 illustrates a method 500 for the processing of a transaction thatutilizes a one-time number via mapping of the one-time number to paymentcredentials of a transaction account.

In step 502, a first transaction request may be received by a receiver(e.g., the receiving device 202) of a processing server (e.g., theprocessing server), wherein the first transaction request includes aplurality of data elements including at least a first data elementconfigured to store a zero transaction amount and a second data elementconfigured to store a primary account number. In step 504, the primaryaccount number stored in the second data element included in thereceived first transaction request may be parsed by the processingserver (e.g., via the receiving device 202 or other module or engine ofthe processing server).

In step 506, a one-time value may be generated by the processing server(e.g., via the generation module 220 thereof), wherein the one-timevalue includes a predetermined number of digits and a subset of thepredetermined number of digits is a reference to the processing server.In step 508, a data entry comprised of at least the parsed primaryaccount number and the generated one-time value may be stored in amemory (e.g., the memory 210) of the processing server (e.g., via thequerying module 218 thereof). In step 510, the generated one-time valuemay be electronically transmitted by a transmitter (e.g., thetransmitting device 224) of the processing server in response to thereceived first transaction request.

In one embodiment, the method 500 may further include: receiving, by thereceiver of the processing server, a second transaction request, whereinthe second transaction request includes a plurality of data elementsincluding at least a first data element configured to store a non-zerotransaction amount and a second data element storing the one-time value;replacing, by the processing server, the one-time value stored in thesecond data element included in the received second transaction requestwith the primary account number; electronically transmitting, by thetransmitter of the processing server; the second transaction request toan issuing financial institution (e.g., the issuing institution 108)based on the primary account number after replacing of the one-timevalue; receiving, by the receiver of the processing server, atransaction response from the issuing financial institution; andforwarding, by the transmitter of the processing server, the transactionresponse in response to the second transaction request. In a furtherembodiment, the second transaction request may be received from a thirdparty entity (e.g., the wallet provider 106). In another furtherembodiment, the first transaction request may be received from acomputing device (e.g., the computing device 104).

In some embodiments, the predetermine number of digits may be 18 or 19.In one embodiment, the subset of the predetermined number of digits maybe 3 or 4. In some embodiments, a remainder of the predetermined numberof digits not included in the subset may be a random or pseudo-randomvalue. In one embodiment, the first transaction request may be formattedaccording to one or more standards governing the interchange offinancial transaction messages.

Computer System Architecture

FIG. 6 illustrates a computer system 600 in which embodiments of thepresent disclosure, or portions thereof, may be implemented ascomputer-readable code. For example, the processing server 102 of FIG. 1may be implemented in the computer system 600 using hardware, software,firmware, non-transitory computer readable media having instructionsstored thereon, or a combination thereof and may be implemented in oneor more computer systems or other processing systems. Hardware,software, or any combination thereof may embody modules and componentsused to implement the methods of FIGS. 3-5.

If programmable logic is used, such logic may execute on a commerciallyavailable processing platform configured by executable software code tobecome a specific purpose computer or a special purpose device (e.g.,programmable logic array, application-specific integrated circuit,etc.). A person having ordinary skill in the art may appreciate thatembodiments of the disclosed subject matter can be practiced withvarious computer system configurations, including multi-coremultiprocessor systems, minicomputers, mainframe computers, computerslinked or clustered with distributed functions, as well as pervasive orminiature computers that may be embedded into virtually any device. Forinstance, at least one processor device and a memory may be used toimplement the above described embodiments.

A processor unit or device as discussed herein may be a singleprocessor, a plurality of processors, or combinations thereof. Processordevices may have one or more processor “cores.” The terms “computerprogram medium,” “non-transitory computer readable medium,” and“computer usable medium” as discussed herein are used to generally referto tangible media such as a removable storage unit 618, a removablestorage unit 622, and a hard disk installed in hard disk drive 612.

Various embodiments of the present disclosure are described in terms ofthis example computer system 600. After reading this description, itwill become apparent to a person skilled in the relevant art how toimplement the present disclosure using other computer systems and/orcomputer architectures. Although operations may be described as asequential process, some of the operations may in fact be performed inparallel, concurrently, and/or in a distributed environment, and withprogram code stored locally or remotely for access by single ormulti-processor machines. In addition, in some embodiments the order ofoperations may be rearranged without departing from the spirit of thedisclosed subject matter.

Processor device 604 may be a special purpose or a general purposeprocessor device specifically configured to perform the functionsdiscussed herein. The processor device 604 may be connected to acommunications infrastructure 606, such as a bus, message queue,network, multi-core message-passing scheme, etc. The network may be anynetwork suitable for performing the functions as disclosed herein andmay include a local area network (LAN), a wide area network (WAN), awireless network (e.g., WiFi), a mobile communication network, asatellite network, the Internet, fiber optic, coaxial cable, infrared,radio frequency (RF), or any combination thereof. Other suitable networktypes and configurations will be apparent to persons having skill in therelevant art. The computer system 600 may also include a main memory 608(e.g., random access memory, read-only memory, etc.), and may alsoinclude a secondary memory 610. The secondary memory 610 may include thehard disk drive 612 and a removable storage drive 614, such as a floppydisk drive, a magnetic tape drive, an optical disk drive, a flashmemory, etc.

The removable storage drive 614 may read from and/or write to theremovable storage unit 618 in a well-known manner. The removable storageunit 618 may include a removable storage media that may be read by andwritten to by the removable storage drive 614. For example, if theremovable storage drive 614 is a floppy disk drive or universal serialbus port, the removable storage unit 618 may be a floppy disk orportable flash drive, respectively. In one embodiment, the removablestorage unit 618 may be non-transitory computer readable recordingmedia.

In some embodiments, the secondary memory 610 may include alternativemeans for allowing computer programs or other instructions to be loadedinto the computer system 600, for example, the removable storage unit622 and an interface 620. Examples of such means may include a programcartridge and cartridge interface (e.g., as found in video gamesystems), a removable memory chip (e.g., EEPROM, PROM, etc.) andassociated socket, and other removable storage units 622 and interfaces620 as will be apparent to persons having skill in the relevant art.

Data stored in the computer system 600 (e.g., in the main memory 608and/or the secondary memory 610) may be stored on any type of suitablecomputer readable media, such as optical storage (e.g., a compact disc,digital versatile disc, Blu-ray disc, etc.) or magnetic tape storage(e.g., a hard disk drive). The data may be configured in any type ofsuitable database configuration, such as a relational database, astructured query language (SQL) database, a distributed database, anobject database, etc. Suitable configurations and storage types will beapparent to persons having skill in the relevant art.

The computer system 600 may also include a communications interface 624.The communications interface 624 may be configured to allow software anddata to be transferred between the computer system 600 and externaldevices. Exemplary communications interfaces 624 may include a modem, anetwork interface (e.g., an Ethernet card), a communications port, aPCMCIA slot and card, etc. Software and data transferred via thecommunications interface 624 may be in the form of signals, which may beelectronic, electromagnetic, optical, or other signals as will beapparent to persons having skill in the relevant art. The signals maytravel via a communications path 626, which may be configured to carrythe signals and may be implemented using wire, cable, fiber optics, aphone line, a cellular phone link, a radio frequency link, etc.

The computer system 600 may further include a display interface 602. Thedisplay interface 602 may be configured to allow data to be transferredbetween the computer system 600 and external display 630. Exemplarydisplay interfaces 602 may include high-definition multimedia interface(HDMI), digital visual interface (DVI), video graphics array (VGA), etc.The display 630 may be any suitable type of display for displaying datatransmitted via the display interface 602 of the computer system 600,including a cathode ray tube (CRT) display, liquid crystal display(LCD), light-emitting diode (LED) display, capacitive touch display,thin-film transistor (TFT) display, etc.

Computer program medium and computer usable medium may refer tomemories, such as the main memory 608 and secondary memory 610, whichmay be memory semiconductors (e.g., DRAMs, etc.). These computer programproducts may be means for providing software to the computer system 600.Computer programs (e.g., computer control logic) may be stored in themain memory 608 and/or the secondary memory 610. Computer programs mayalso be received via the communications interface 624. Such computerprograms, when executed, may enable computer system 600 to implement thepresent methods as discussed herein. In particular, the computerprograms, when executed, may enable processor device 604 to implementthe methods illustrated by FIGS. 3-5, as discussed herein. Accordingly,such computer programs may represent controllers of the computer system600. Where the present disclosure is implemented using software, thesoftware may be stored in a computer program product and loaded into thecomputer system 600 using the removable storage drive 614, interface620, and hard disk drive 612, or communications interface 624.

The processor device 604 may comprise one or more modules or enginesconfigured to perform the functions of the computer system 600. Each ofthe modules or engines may be implemented using hardware and, in someinstances, may also utilize software, such as corresponding to programcode and/or programs stored in the main memory 608 or secondary memory610. In such instances, program code may be compiled by the processordevice 604 (e.g., by a compiling module or engine) prior to execution bythe hardware of the computer system 600. For example, the program codemay be source code written in a programming language that is translatedinto a lower level language, such as assembly language or machine code,for execution by the processor device 604 and/or any additional hardwarecomponents of the computer system 600. The process of compiling mayinclude the use of lexical analysis, preprocessing, parsing, semanticanalysis, syntax-directed translation, code generation, codeoptimization, and any other techniques that may be suitable fortranslation of program code into a lower level language suitable forcontrolling the computer system 600 to perform the functions disclosedherein. It will be apparent to persons having skill in the relevant artthat such processes result in the computer system 600 being a speciallyconfigured computer system 600 uniquely programmed to perform thefunctions discussed above.

Techniques consistent with the present disclosure provide, among otherfeatures, systems and methods for facilitating a transaction with aone-time number. While various exemplary embodiments of the disclosedsystem and method have been described above it should be understood thatthey have been presented for purposes of example only, not limitations.It is not exhaustive and does not limit the disclosure to the preciseform disclosed. Modifications and variations are possible in light ofthe above teachings or may be acquired from practicing of thedisclosure, without departing from the breadth or scope.

What is claimed is:
 1. A method for facilitating a transaction with aone-time number, comprising: prior to a transaction occurring between aconsumer and a merchant, receiving, by a receiver of a processingserver, a first transaction request from a computing device of theconsumer without utilizing payment network infrastructure, wherein thefirst transaction request includes a plurality of data elementsincluding at least a first data element storing a zero transactionamount and a second data element storing a primary account number, andwherein the merchant and the processing server are separate and distinctentities; based on the zero transaction amount stored in the first dataelement, determining, by the processing server that the firsttransaction request, received from the computing device of the consumer,is a request for a one-time value; parsing, by the processing server,the primary account number stored in the second data element included inthe first transaction request received from the computing device of theconsumer; generating, by the processing server, the one-time value,wherein the one-time value includes a predetermined number of digits,and a subset of the predetermined number of digits is a reference to theprocessing server; storing, in a memory of the processing server, a dataentry comprised of at least the parsed primary account number and thegenerated one-time value; and electronically transmitting, by atransmitter of the processing server, the generated one-time value, inresponse to the received first transaction request, to the computingdevice of the consumer for use in a financial transaction.
 2. The methodof claim 1, wherein the predetermined number of digits is 18 or
 19. 3.The method of claim 1, wherein the subset of the predetermined number ofdigits is 3 or
 4. 4. The method of claim 1, wherein the plurality ofdata elements further includes a third data element storingauthentication data, and the method further comprises: validating, bythe processing server, the authentication data against a transactionaccount associated with the primary account number, where the one-timevalue is generated upon successful validation.
 5. The method of claim 1,wherein the first transaction request is formatted according to one ormore standards governing the interchange of financial transactionmessages.
 6. A system for facilitating a transaction with a one-timenumber, comprising: a receiver, of a processing server, configured toreceive a first transaction request from a computing device of aconsumer prior to a transaction occurring between the consumer and amerchant, wherein the first transaction request includes a plurality ofdata elements including at least a first data element storing a zerotransaction amount and a second data element storing a primary accountnumber, and wherein the processing server and the merchant are separateand distinct entities; a processing device, of the processing server,configured to determine, based on the zero transaction amount stored inthe first data element of the first transaction request received fromthe computing device of the consumer, that the first transaction requestis a request for a one-time value; parse the primary account numberstored in the second data element included in the first transactionrequest received from the computing device of the consumer, and generatethe one-time value, wherein the one-time value includes a predeterminednumber of digits and a subset of the predetermined number of digits is areference to the processing server; a memory, of the processing server,configured to store a data entry comprised of at least the parsedprimary account number and the generated one-time value; and atransmitter, of the processing server, configured to electronicallytransmit the generated one-time value, to the computing device of theconsumer for use in a financial transaction, in response to the receivedfirst transaction request.
 7. The system of claim 6, wherein thepredetermined number of digits is 18 or
 19. 8. The system of claim 6,wherein the subset of the predetermined number of digits is 3 or
 4. 9.The system of claim 6, wherein the plurality of data elements furtherincludes a third data element storing authentication data, theprocessing server is further configured to validate the authenticationdata against a transaction account associated with the primary accountnumber, and the one-time value is generated upon successful validationof the authentication data.
 10. The system of claim 6, wherein the firsttransaction request is formatted according to one or more standardsgoverning the interchange of financial transaction messages.